Repository navigation
Grouped root 'docker-compose.yml' container image updates with the other container images. - #3164
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Important Review skippedReview was skipped as selected files did not have any reviewable changes. ⛔ Files ignored due to path filters (1)
⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Team Run ID: ⛔ Files ignored due to path filters (1)
You can disable this status message by setting the Use the checkbox below for a quick retry:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Team Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: 4 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour. WalkthroughThe container-image package rule now matches ChangesContainer image matching
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Feature Merge Risk: ⚪ Minimal · up to The change is limited to matching the root Compose file for the existing container-image rule; no material merge risk is evident from the supplied review context. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🧪 Generate unit tests (beta)
🛠️ Fix failing CI checks 💡
A rabbit checks the paths with care Comment |
This comment has been minimized.
This comment has been minimized.
|
📖 Documentation preview for this pull request has been deployed to Netlify: https://6ab9941efb745b02671e0a6c--vortex-docs.netlify.app This preview is rebuilt on every commit and is not the production documentation site. |
This comment has been minimized.
This comment has been minimized.
982fc0d to
1041a98
Compare
|
Code coverage (threshold: 90%) Per-class coverage |
This comment has been minimized.
This comment has been minimized.
2 similar comments
This comment has been minimized.
This comment has been minimized.
|
Code coverage (threshold: 90%) Per-class coverage |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3164 +/- ##
==========================================
- Coverage 87.02% 86.65% -0.37%
==========================================
Files 114 106 -8
Lines 5255 5089 -166
Branches 49 3 -46
==========================================
- Hits 4573 4410 -163
+ Misses 682 679 -3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Summary
The
Container images - All - Major, minor and patchpackage rule inrenovate.jsonnow matchesdocker-compose.ymlin itsmatchFileNamesarray alongside.docker/**,.circleci/**and.github/workflows/**, so the four container image pins in the rootdocker-compose.ymljoin the same grouped rule as the.docker/**pins.The rule's
matchFileNamesnever listeddocker-compose.yml, even thoughdocker-composeis one of Renovate'senabledManagersand acustomManagersregex already tracks theIMAGE:build arg in that file, so every image bump Renovate found there -uselagoon/mysql-8.4on thedatabasebuild arg and thedatabase2image,uselagoon/valkey-8onredis,selenium/standalone-chromium, anddrevops/docker-wait-for-dependencies- fell through to Renovate's defaults: one PR per dependency, with noschedule.New Lagoon image releases now produce a single grouped PR on the
before 3amschedule instead of splittinguselagoon/mysql-8.4anduselagoon/valkey-8into separate unscheduled PRs alongside it, anduselagoon/mysql-8.4- pinned in bothdocker-compose.ymland.docker/database.dockerfile- no longer updates across two different PRs in the same cycle; no image version, manager, or other package rule changes in this PR.Before / After
Changes
renovate.json: added"docker-compose.yml"to thematchFileNamesarray of theContainer images - All - Major, minor and patchpackage rule..vortex/installer/tests/Fixtures/handler_process/_baseline/renovate.json: same one-line addition, kept byte-for-byte identical to the shipped rootrenovate.jsonsince the installer fixture is a snapshot of it.Summary by CodeRabbit